Repository navigation
feat: point prototype and visualization at /user-interface:write-css - #7089
Conversation
…talled Adds a presence-gated pointer in explore-directions and visualize, with a changelog fragment for each plugin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Claude finished @kyle-sexton's task in 2m 35s —— View job Review in progress
|
|
Claude finished @kyle-sexton's task in 27s —— View job Security review: no issues found
Skip gate applied. This PR's diff (
All four changes are pure additions (no deletions, no narrowing of existing guidance), contain no code, no input handling, no secrets/tokens, no authz logic, and no GitHub Actions changes. There is no instruction-surface deletion here (the diff only adds a conditional pointer to another skill), so the instruction-exception-register check does not apply. No security-relevant surface — review stops here per the skip gate. No findings. |
|
claude-security-review has reviewed this pull request through 77022dd; a later push is reviewed from there. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7d62133a65
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
claude-review has reviewed this pull request through 77022dd; a later push is reviewed from there. |
explore-directions now points only real-stack variant CSS at /user-interface:write-css; HTML mockups keep their declared directions. visualize limits the pointer to CSS outside the bundled page chrome. Both say to write the CSS in-skill when write-css is not installed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Claude finished @kyle-sexton's task in 5m 8s —— View job Code review: no issues found
Scope. Incremental review of the fix-up commit ( This commit resolves all three issues raised by the prior Codex review and the author's own self-review:
I had a second pass adversarially check whether that last "either way" clause newly conflicts with the pre-existing Step 5 product-UI exception (which says to match a product's own styling "rather than the plugin chrome"). It doesn't: "either way" grammatically refers back to the write-css-installed/not-installed pair in the same sentence, not to Step 5's separate subject-matter axis, so there's no real ambiguity introduced here. Changelog fragments accurately reflect the actual wording changes. No findings to post. |
|
Claude finished @kyle-sexton's task in 38s —— View job Security review: no issues found
Scope. Per the lane header, this pass reviews only what changed since
Skip gate applied. The incremental diff only reworks skill prose addressing the three prior review findings (Codex P1/P2, and the author's own verified fixes):
This is a pure prose/scope refinement — no deletion or narrowing of a standing instruction (the instruction-surface-deletion lens doesn't apply; if anything these changes add a fallback and narrow the delegation's reach, which tightens rather than loosens guardrails). No code, no input handling, no secrets/tokens, no authz logic, and no GitHub Actions changes. The full-PR surface was already reviewed clean at No security-relevant surface — review stops here per the skip gate. No findings. |

No related issue: last step of the good-css absorption; write-css landed in #7060
Summary
Two skills that hand-author CSS now point that work at
/user-interface:write-csswhen it is installed, so project-facing CSS applies the project's design system and conventions first. Throwaway HTML mockups and the bundled page chrome keep their own governing inputs.Fix
plugins/prototype/skills/explore-directions/SKILL.md(Process, step 2):plugins/visualization/skills/visualize/SKILL.md(Step 2: Pick the form):.changes/prototype/and.changes/visualization/.Verification
grep -c "user-interface:write-css": 1 in each SKILL.md.plugins/skill-quality/scripts/check-skill.sh plugins/prototype/skills plugins/visualization/skills: 4 passed, 0 failed (exit 0; warnings are pre-existing size/description advisories).scripts/check-changelog-fragments.sh --check-required origin/main: every fragment-mode plugin changed (2) has a fragment.Related
🤖 Generated with Claude Code